Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners

ICTPRG526 Mapping and Delivery Guide
Maintain functionality of legacy code programs

Version 1.0
Issue Date: April 2024


Qualification -
Unit of Competency ICTPRG526 - Maintain functionality of legacy code programs
Description
Employability Skills
Learning Outcomes and Application This unit describes the skills and knowledge required to maintain the functionality of legacy code programs.It applies to individuals working in software development who are required to maintain legacy programs, updating them as required.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Duration and Setting X weeks, nominally xx hours, delivered in a classroom/online/blended learning setting.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

documents detailing the organisational standards for software development

the existing legacy code

appropriate compilers

the appropriate learning and assessment support.

Assessors must satisfy NVR/AQTF assessor requirements.
Prerequisites/co-requisites
Competency Field
Development and validation strategy and guide for assessors and learners Student Learning Resources Handouts
Activities 		Slides
PPT 		Assessment 1 Assessment 2 Assessment 3 Assessment 4
Elements of Competency Performance Criteria              
Element: Determine the functional changes required
  • Consult the user to determine, and document, the functional change required
  • Clarify the impact of changes with operational personnel
       
Element: Review legacy language
  • Identify the basic structures of the legacy language
  • Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling
  • Review the basic algorithms of the legacy language
       
Element: Identify and isolate the change
  • Review the technical documentation for the system, to determine which modules to change
  • Review the source code to determine program logic and flow
  • Update the technical documentation to reflect the current state of the program
       
Element: Determine the framework for change
  • Determine the change approach to be used to implement the change
  • Ascertain and detail the risks for each approach
  • Determine the personnel who will make the changes
       
Element: Design the change
  • Develop the changes required, considering the impact of the changes on other parts of the system
  • Document the changes according to change-management standards
       
Element: Code the change
  • Identify and obtain, the appropriate hardware and software for the change
  • Write the code according to programming standards
  • Compile and unit test the changes
  • Document the changes according to programming standards
       
Element: Test the change
  • System test the changes and record the outcomes
  • Perform user acceptance testing and record the outcomes
  • Sign off the change request
       
Element: Archive the system
  • Create a new version of software, according to configuration management standards
  • Archive the development system, including the source code, compilers and test data
       


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the functional changes required

1.1 Consult the user to determine, and document, the functional change required

1.2 Clarify the impact of changes with operational personnel

2. Review legacy language

2.1 Identify the basic structures of the legacy language

2.2 Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling

2.3 Review the basic algorithms of the legacy language

3. Identify and isolate the change

3.1 Review the technical documentation for the system, to determine which modules to change

3.2 Review the source code to determine program logic and flow

3.3 Update the technical documentation to reflect the current state of the program

4. Determine the framework for change

4.1 Determine the change approach to be used to implement the change

4.2 Ascertain and detail the risks for each approach

4.3 Determine the personnel who will make the changes

5. Design the change

5.1 Develop the changes required, considering the impact of the changes on other parts of the system

5.2 Document the changes according to change-management standards

6. Code the change

6.1 Identify and obtain, the appropriate hardware and software for the change

6.2 Write the code according to programming standards

6.3 Compile and unit test the changes

6.4 Document the changes according to programming standards

7. Test the change

7.1 System test the changes and record the outcomes

7.2 Perform user acceptance testing and record the outcomes

7.3 Sign off the change request

8. Archive the system

8.1 Create a new version of software, according to configuration management standards

8.2 Archive the development system, including the source code, compilers and test data

Evidence of the ability to:

read legacy language

identify and isolate the required change

implement the change via the chosen technique.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain operational procedures on the required operating system

outline the organisational standards for software development

define security and viruses

identify privacy legislation and copyright with regard to the legacy code, the particular system involved and its data

define the technical terminology related to reading help files and manuals

outline different types of software.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assignment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Determine the functional changes required

1.1 Consult the user to determine, and document, the functional change required

1.2 Clarify the impact of changes with operational personnel

2. Review legacy language

2.1 Identify the basic structures of the legacy language

2.2 Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling

2.3 Review the basic algorithms of the legacy language

3. Identify and isolate the change

3.1 Review the technical documentation for the system, to determine which modules to change

3.2 Review the source code to determine program logic and flow

3.3 Update the technical documentation to reflect the current state of the program

4. Determine the framework for change

4.1 Determine the change approach to be used to implement the change

4.2 Ascertain and detail the risks for each approach

4.3 Determine the personnel who will make the changes

5. Design the change

5.1 Develop the changes required, considering the impact of the changes on other parts of the system

5.2 Document the changes according to change-management standards

6. Code the change

6.1 Identify and obtain, the appropriate hardware and software for the change

6.2 Write the code according to programming standards

6.3 Compile and unit test the changes

6.4 Document the changes according to programming standards

7. Test the change

7.1 System test the changes and record the outcomes

7.2 Perform user acceptance testing and record the outcomes

7.3 Sign off the change request

8. Archive the system

8.1 Create a new version of software, according to configuration management standards

8.2 Archive the development system, including the source code, compilers and test data

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Consult the user to determine, and document, the functional change required 
Clarify the impact of changes with operational personnel 
Identify the basic structures of the legacy language 
Review the data storage of the legacy language with regard to global variables, modularisation, cohesion and coupling 
Review the basic algorithms of the legacy language 
Review the technical documentation for the system, to determine which modules to change 
Review the source code to determine program logic and flow 
Update the technical documentation to reflect the current state of the program 
Determine the change approach to be used to implement the change 
Ascertain and detail the risks for each approach 
Determine the personnel who will make the changes 
Develop the changes required, considering the impact of the changes on other parts of the system 
Document the changes according to change-management standards 
Identify and obtain, the appropriate hardware and software for the change 
Write the code according to programming standards 
Compile and unit test the changes 
Document the changes according to programming standards 
System test the changes and record the outcomes 
Perform user acceptance testing and record the outcomes 
Sign off the change request 
Create a new version of software, according to configuration management standards 
Archive the development system, including the source code, compilers and test data 

Forms

Assessment Cover Sheet

ICTPRG526 - Maintain functionality of legacy code programs
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG526 - Maintain functionality of legacy code programs

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: